Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0205

reference: 187-tree-1
name: 0205
tree-preservation-order: undefined
187-tpo-1
uprn
address-text
point: POINT (-0.940737 50.864196)
geometry: MULTIPOLYGON (((-0.940680 50.864190,-0.940682 50.864201,-0.940690 50.864211,-0.940703 50.864219,-0.940718 50.864225,-0.940736 50.864227,-0.940753 50.864225,-0.940769 50.864220,-0.940782 50.864212,-0.940790 50.864202,-0.940794 50.864191,-0.940791 50.864180,-0.940783 50.864170,-0.940771 50.864162,-0.940755 50.864157,-0.940738 50.864155,-0.940720 50.864156,-0.940704 50.864161,-0.940691 50.864169,-0.940683 50.864179,-0.940680 50.864190)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL